{"action":"created","issue":{"url":"https://api.github.com/repos/chapel-lang/chapel/issues/9671","repository_url":"https://api.github.com/repos/chapel-lang/chapel","labels_url":"https://api.github.com/repos/chapel-lang/chapel/issues/9671/labels{/name}","comments_url":"https://api.github.com/repos/chapel-lang/chapel/issues/9671/comments","events_url":"https://api.github.com/repos/chapel-lang/chapel/issues/9671/events","html_url":"https://github.com/chapel-lang/chapel/issues/9671","id":327520824,"number":9671,"title":"Spike. Investigate alternatives to using Chapel's Cray-internal Whiteboxes","user":{"login":"awallace-cray","id":16021421,"avatar_url":"https://avatars0.githubusercontent.com/u/16021421?v=4","gravatar_id":"","url":"https://api.github.com/users/awallace-cray","html_url":"https://github.com/awallace-cray","followers_url":"https://api.github.com/users/awallace-cray/followers","following_url":"https://api.github.com/users/awallace-cray/following{/other_user}","gists_url":"https://api.github.com/users/awallace-cray/gists{/gist_id}","starred_url":"https://api.github.com/users/awallace-cray/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awallace-cray/subscriptions","organizations_url":"https://api.github.com/users/awallace-cray/orgs","repos_url":"https://api.github.com/users/awallace-cray/repos","events_url":"https://api.github.com/users/awallace-cray/events{/privacy}","received_events_url":"https://api.github.com/users/awallace-cray/received_events","type":"User","site_admin":false},"labels":[{"id":496591435,"url":"https://api.github.com/repos/chapel-lang/chapel/labels/area:%20BTR","name":"area: BTR","color":"d4c5f9","default":false}],"state":"open","locked":false,"assignee":{"login":"awallace-cray","id":16021421,"avatar_url":"https://avatars0.githubusercontent.com/u/16021421?v=4","gravatar_id":"","url":"https://api.github.com/users/awallace-cray","html_url":"https://github.com/awallace-cray","followers_url":"https://api.github.com/users/awallace-cray/followers","following_url":"https://api.github.com/users/awallace-cray/following{/other_user}","gists_url":"https://api.github.com/users/awallace-cray/gists{/gist_id}","starred_url":"https://api.github.com/users/awallace-cray/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awallace-cray/subscriptions","organizations_url":"https://api.github.com/users/awallace-cray/orgs","repos_url":"https://api.github.com/users/awallace-cray/repos","events_url":"https://api.github.com/users/awallace-cray/events{/privacy}","received_events_url":"https://api.github.com/users/awallace-cray/received_events","type":"User","site_admin":false},"assignees":[{"login":"awallace-cray","id":16021421,"avatar_url":"https://avatars0.githubusercontent.com/u/16021421?v=4","gravatar_id":"","url":"https://api.github.com/users/awallace-cray","html_url":"https://github.com/awallace-cray","followers_url":"https://api.github.com/users/awallace-cray/followers","following_url":"https://api.github.com/users/awallace-cray/following{/other_user}","gists_url":"https://api.github.com/users/awallace-cray/gists{/gist_id}","starred_url":"https://api.github.com/users/awallace-cray/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awallace-cray/subscriptions","organizations_url":"https://api.github.com/users/awallace-cray/orgs","repos_url":"https://api.github.com/users/awallace-cray/repos","events_url":"https://api.github.com/users/awallace-cray/events{/privacy}","received_events_url":"https://api.github.com/users/awallace-cray/received_events","type":"User","site_admin":false}],"milestone":{"url":"https://api.github.com/repos/chapel-lang/chapel/milestones/21","html_url":"https://github.com/chapel-lang/chapel/milestone/21","labels_url":"https://api.github.com/repos/chapel-lang/chapel/milestones/21/labels","id":3384954,"number":21,"title":"J Sprint 7","description":"","creator":{"login":"benjamin-robbins","id":30993993,"avatar_url":"https://avatars1.githubusercontent.com/u/30993993?v=4","gravatar_id":"","url":"https://api.github.com/users/benjamin-robbins","html_url":"https://github.com/benjamin-robbins","followers_url":"https://api.github.com/users/benjamin-robbins/followers","following_url":"https://api.github.com/users/benjamin-robbins/following{/other_user}","gists_url":"https://api.github.com/users/benjamin-robbins/gists{/gist_id}","starred_url":"https://api.github.com/users/benjamin-robbins/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benjamin-robbins/subscriptions","organizations_url":"https://api.github.com/users/benjamin-robbins/orgs","repos_url":"https://api.github.com/users/benjamin-robbins/repos","events_url":"https://api.github.com/users/benjamin-robbins/events{/privacy}","received_events_url":"https://api.github.com/users/benjamin-robbins/received_events","type":"User","site_admin":false},"open_issues":19,"closed_issues":0,"state":"open","created_at":"2018-05-29T17:56:45Z","updated_at":"2018-05-30T01:05:34Z","due_on":"2018-06-12T07:00:00Z","closed_at":null},"comments":0,"created_at":"2018-05-29T23:23:43Z","updated_at":"2018-05-30T16:22:18Z","closed_at":null,"author_association":"MEMBER","body":"The obsolete software (SLES-11/CLE-5) and hardware (Westmere CPU) in Chapel's Cray-internal Whitebox systems esxbld03/04; together with weak support for these systems within Cray itself; have long been a source of problems for Chapel when trying to use esxbld's for nightly testing. \r\n\r\nFor example, we were forced to move Cray compiler (cce) \"Whitebox\" testing from esxbld03/04 to kay-elogin, because recent versions of cce no longer support Westmere. \r\n\r\nAnother example: the last two major releases of the PGI compiler will not work with SLES-11 system binaries. Chapel's \"Whitebox\" testing for PGI now runs with a very old version of PGI. \r\n\r\nThe most recent example is https://github.com/chapel-lang/chapel/issues/9645 : Chapel build + test errors on Cray-internal Whitebox, since last PE update 5/26\r\n\r\nFurthermore, Chapel's WB testing does not directly support any deliverable. It does exercise Chapel's compiler support in a general way, and it might expose a new problem sooner than if there were no such testing. Chapel's WB testing for icc (Intel compiler) duplicates and extends the test coverage we already get elsewhere (Cray-module testing). For PGI compilers, the WB is our only source of test coverage; but Chapel no longer officially supports PGI anyway.  We already test with gcc (GNU compiler) on all kinds of Linux machines; however, the only way to test gcc in the presence of the Cray PrgEnv is to test on an actual Cray or a WB system, and Chapel's WB testing did provide useful additional horsepower for that test coverage. \r\n\r\nBefore trying to fix https://github.com/chapel-lang/chapel/issues/9645, we should find out if other alternatives exist within Cray, that could be used to accomplish the same goals as the existing WB testing, but with less trouble. \r\n\r\nThis task should investigate at least the following:\r\n* Summarize the existing Whitebox test configs (Host/Target Compilers, Comm, Platform, etc).  How long do these test configs actually run on the current Whiteboxes?  \r\n* We have already moved the cce Whitebox test configs from esxbld03/04 to kay-login.  What other Cray-internal \"elogin\" machines could we use in a similar way, to offload more testing from esxbld03/04?  (BTW, kay-elogin is already pretty busy)\r\n* Another suggestion was to run icc \"Whitebox\" tests on a regular Cray-internal Linux system where icc was installed.  Do systems like that exist, and would we be allowed to use them? \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/chapel-lang/chapel/issues/comments/393224818","html_url":"https://github.com/chapel-lang/chapel/issues/9671#issuecomment-393224818","issue_url":"https://api.github.com/repos/chapel-lang/chapel/issues/9671","id":393224818,"user":{"login":"awallace-cray","id":16021421,"avatar_url":"https://avatars0.githubusercontent.com/u/16021421?v=4","gravatar_id":"","url":"https://api.github.com/users/awallace-cray","html_url":"https://github.com/awallace-cray","followers_url":"https://api.github.com/users/awallace-cray/followers","following_url":"https://api.github.com/users/awallace-cray/following{/other_user}","gists_url":"https://api.github.com/users/awallace-cray/gists{/gist_id}","starred_url":"https://api.github.com/users/awallace-cray/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/awallace-cray/subscriptions","organizations_url":"https://api.github.com/users/awallace-cray/orgs","repos_url":"https://api.github.com/users/awallace-cray/repos","events_url":"https://api.github.com/users/awallace-cray/events{/privacy}","received_events_url":"https://api.github.com/users/awallace-cray/received_events","type":"User","site_admin":false},"created_at":"2018-05-30T16:22:18Z","updated_at":"2018-05-30T16:22:18Z","author_association":"MEMBER","body":"2018-05-30 09:15 \r\nDepending on the results, a followup question:  If we did find additional machines like kay-elogin, would it make sense to use the Cray-module correctness test jobs we already have, but run them over the full Chapel test suite instead of just release/examples/**?  \r\n* Do the existing \"Whitebox\" test configs provide different or better test coverage than we would get by running the same set of Chapel tests as Cray-module correctness test configs? \r\n* If we could abandon the Jenkins job configs and Chapel build scripts used by the \"Whitebox\" correctness tests, it would reduce the amount of complex, Cray-specific build goo we need to support. \r\n"}}
{"actor":{"display_login":"awallace-cray"}}