test: remove --no-warnings flag

This change should have no effect since the test does not appear to emit any warnings. If there are warnings, we probably should handle them properly instead of passing this flag to the runtime. Refs: #35093 PR-URL: #58424 Reviewed-By: Juan José Arboleda <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Filip Skokan <[email protected]>

Author: tniessen

test/parallel/test-crypto-authenticated.js

@@ -18,7 +18,7 @@
 // DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
 // OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
 // USE OR OTHER DEALINGS IN THE SOFTWARE.
-// Flags: --no-warnings
+
 'use strict';
 constcommon=require('../common');
 if(!common.hasCrypto){