[SERVER-29243] move jsHeapLimit.js from core to noPassthrough Created: 16/May/17  Updated: 30/Oct/23  Resolved: 03/Oct/17

Status: Closed
Project: Core Server
Component/s: JavaScript
Affects Version/s: 3.5.7
Fix Version/s: 3.6.0-rc0

Type: Task Priority: Minor - P4
Reporter: Robert Guo (Inactive) Assignee: Eddie Louie
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: TIG 2017-10-23
Participants:

 Description   

This test spins up its own mongod, so it should not be in jsCore



 Comments   
Comment by Githook User [ 03/Oct/17 ]

Author:

{'email': 'eddie.louie@mongodb.com', 'name': 'Eddie Louie', 'username': 'elouie99'}

Message: SERVER-29243 Move jsHeapLimit.js from core to noPassthrough

Plus add overrides for runMongod, ShardingTest and ReplSetTest to
throw error if any js test in core.yml tries to use these to start
their own mongod.
Branch: master
https://github.com/mongodb/mongo/commit/6ed8e31519f14f163606f17199f4cb9b0dccf281

Comment by Max Hirschhorn [ 18/May/17 ]

We should also consider defining an override for MongoRunner.runMongod(), etc. when running in the core.yml test suite that throws an error to avoid this kind of situation in the future.

Generated at Thu Feb 08 04:20:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.