Closed Bug 1179955 Opened 9 years ago Closed 9 years ago

Turn on a GTest job in automation

Categories

(Testing :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: chmanchester, Assigned: chmanchester)

References

Details

Attachments

(1 file)

I was able to get them running from mozharness locallly, I'd like to enable them on try (or ash, or wherever) to test my work.
What's the full runtime for GTest these days? When I added it the overhead of doing a job for it would of been much much higher than just running it in the build phase.
Quickly looking at logs it's about 3 minutes, so I guess we could combine them with the Cpp job (which already finishes in under 15 minutes).
Ok, I'd like to enable a job on try that runs gtests and cppunittests in the same job while we get things up and running, then turn off the cppunittest job when these are ready to be turned on everywhere.

Builders added:
+ Rev4 MacOSX Snow Leopard 10.6 try debug test cpp_gtest
+ Rev4 MacOSX Snow Leopard 10.6 try opt test cpp_gtest
+ Rev5 MacOSX Mountain Lion 10.8 try debug test cpp_gtest
+ Rev5 MacOSX Mountain Lion 10.8 try opt test cpp_gtest
+ Rev5 MacOSX Yosemite 10.10 try debug test cpp_gtest
+ Rev5 MacOSX Yosemite 10.10 try opt test cpp_gtest
+ Ubuntu ASAN VM 12.04 x64 try opt test cpp_gtest
+ Ubuntu Code Coverage VM 12.04 x64 try opt test cpp_gtest
+ Ubuntu VM 12.04 try debug test cpp_gtest
+ Ubuntu VM 12.04 try opt test cpp_gtest
+ Ubuntu VM 12.04 try pgo test cpp_gtest
+ Ubuntu VM 12.04 x64 try debug test cpp_gtest
+ Ubuntu VM 12.04 x64 try opt test cpp_gtest
+ Ubuntu VM 12.04 x64 try pgo test cpp_gtest
+ Windows 7 32-bit try debug test cpp_gtest
+ Windows 7 32-bit try opt test cpp_gtest
+ Windows 7 32-bit try pgo test cpp_gtest
+ Windows 8 64-bit try debug test cpp_gtest
+ Windows 8 64-bit try opt test cpp_gtest
+ Windows 8 64-bit try pgo test cpp_gtest
+ Windows XP 32-bit try debug test cpp_gtest
+ Windows XP 32-bit try opt test cpp_gtest
+ Windows XP 32-bit try pgo test cpp_gtest
I'd like to turn these on so I can test a new job on try (I'll keep these hidden as they won't do anything interesting until the mozharness changes land). Let me know if this plan makes sense, or we'd be better of starting on a project branch.
Attachment #8629113 - Flags: review?(rail)
Assignee: nobody → cmanchester
Status: NEW → ASSIGNED
Attachment #8629113 - Flags: review?(rail) → review+
(In reply to Benoit Girard (:BenWa) from comment #1)
> What's the full runtime for GTest these days? When I added it the overhead
> of doing a job for it would of been much much higher than just running it in
> the build phase.

There's another benefit to splitting it to its own test job--if it fails, sheriffs can retrigger it without having to retrigger a whole build.
Good point
Cpp-G is showing up on try now, I can work from there.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Depends on: 1192857
You need to log in before you can comment on or make changes to this bug.