Build failed in Jenkins: pgadmin4-master-python27 #604

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Using the 'webcabin-docker' from new repository, which contains 
fixed

[Ashesh Vashi] Change the order of the shims in the shims file.

--
[...truncated 665.43 KB...]
PgAgentStatsTestCase (Check the stats of pgAgent job)
PgAgentAddTestCase (Add pgAgent job)
SynonymDeleteTestCase (Fetch synonym Node URL)
ResourceGroupsAddTestCase (Add resource groups)
PackagePutTestCase (Fetch Package Node URL)
SynonymPutTestCase (Fetch synonym Node URL)
ResourceGroupsPutTestCase (Put resource groups)
TestSSLConnection (Test for SSL connection)
PgAgentGetTestCase (Get pgAgent job)
ResourceGroupsDeleteTestCase (Delete resource groups)
SynonymAddTestCase (Default Node URL)
ResourceGroupsGetTestCase (Get resource groups)
PgAgentDeleteTestCase (Delete pgAgent job)
PackageGetTestCase (Fetch Package Node URL)

EDB Postgres AS 9.4:

305 tests passed
0 tests failed
8 tests skipped:
PgAgentGetTestCase (Get pgAgent job)
TestSSLConnection (Test for SSL connection)
PgAgentStatsTestCase (Check the stats of pgAgent job)
TableUpdateTestCase (Detach partition from existing list 
partitioned table,
Create partitions of existing range 
partitioned table,
Detach partition from existing range 
partitioned table,
Attach partition to existing range 
partitioned table,
Attach partition to existing list 
partitioned table,
Create partitions of existing list 
partitioned table)
PgAgentAddTestCase (Add pgAgent job)
PgAgentDeleteTestCase (Delete pgAgent job)
PgAgentPutTestCase (Put pgAgent job)
TableAddTestCase (Create Range partitioned table with 2 
partitions,
Create List partitioned table with 2 
partitions)

EDB Postgres AS 9.5:

305 tests passed
0 tests failed
8 tests skipped:
PgAgentGetTestCase (Get pgAgent job)
TestSSLConnection (Test for SSL connection)
PgAgentStatsTestCase (Check the stats of pgAgent job)
TableUpdateTestCase (Detach partition from existing list 
partitioned table,
Create partitions of existing range 
partitioned table,
Detach partition from existing range 
partitioned table,
Attach partition to existing range 
partitioned table,
Attach partition to existing list 
partitioned table,
Create partitions of existing list 
partitioned table)
PgAgentAddTestCase (Add pgAgent job)
PgAgentDeleteTestCase (Delete pgAgent job)
PgAgentPutTestCase (Put pgAgent job)
TableAddTestCase (Create Range partitioned table with 2 
partitions,
Create List partitioned table with 2 
partitions)

EDB Postgres AS 9.6:

305 tests passed
0 tests failed
8 tests skipped:
PgAgentGetTestCase (Get pgAgent job)
TestSSLConnection (Test for SSL connection)
PgAgentStatsTestCase (Check the stats of pgAgent job)
TableUpdateTestCase (Detach partition from existing list 
partitioned table,
Create partitions of existing range 
partitioned table,
Detach partition from existing range 
partitioned table,
Attach partition to existing range 
partitioned table,
Attach partition to existing list 
partitioned table,
Create partitions of existing list 
partitioned table)
PgAgentAddTestCase (Add pgAgent job)
PgAgentDeleteTestCase (Delete pgAgent job)
PgAgentPutTestCase (Put pgAgent job)
TableAddTestCase (Create Range partitioned table with 2 
partitions,
Create List partitioned table with 2 
partitions)

EDB Postgres AS 9.2:

293 tests passed
0 tests failed
20 tests skipped:
TestSSLConnection (Test for SSL connection)
PgAgentStatsTestCase (Check the stats of pgAgent job)
Tab

Build failed in Jenkins: pgadmin4-master-python35 #602

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Using the 'webcabin-docker' from new repository, which contains 
fixed

[Ashesh Vashi] Change the order of the shims in the shims file.

[Ashesh Vashi] Using the latest version (v2.3.0) of jquery.event.drag to fix the

--
[...truncated 703.38 KB...]
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 327 of 531 SUCCESS (0 secs 
/ 5.454 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 328 of 531 SUCCESS (0 secs 
/ 5.458 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 329 of 531 SUCCESS (0 secs 
/ 5.461 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 330 of 531 SUCCESS (0 secs 
/ 5.464 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 331 of 531 SUCCESS (0 secs 
/ 5.467 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 332 of 531 SUCCESS (0 secs 
/ 5.472 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 333 of 531 SUCCESS (0 secs 
/ 5.475 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 334 of 531 SUCCESS (0 secs 
/ 5.479 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 335 of 531 SUCCESS (0 secs 
/ 5.485 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 336 of 531 SUCCESS (0 secs 
/ 5.49 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 337 of 531 SUCCESS (0 secs 
/ 5.493 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 338 of 531 SUCCESS (0 secs 
/ 5.496 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 339 of 531 SUCCESS (0 secs 
/ 5.499 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 340 of 531 SUCCESS (0 secs 
/ 5.501 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 341 of 531 SUCCESS (0 secs 
/ 5.505 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 342 of 531 SUCCESS (0 secs 
/ 5.508 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 343 of 531 SUCCESS (0 secs 
/ 5.512 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 344 of 531 SUCCESS (0 secs 
/ 5.519 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 345 of 531 SUCCESS (0 secs 
/ 5.522 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 346 of 531 SUCCESS (0 secs 
/ 5.525 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 347 of 531 SUCCESS (0 secs 
/ 5.528 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 348 of 531 SUCCESS (0 secs 
/ 5.531 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 349 of 531 SUCCESS (0 secs 
/ 5.535 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 350 of 531 SUCCESS (0 secs 
/ 5.54 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 351 of 531 SUCCESS (0 secs 
/ 5.545 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 352 of 531 SUCCESS (0 secs 
/ 5.551 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 353 of 531 SUCCESS (0 secs 
/ 5.554 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 354 of 531 SUCCESS (0 secs 
/ 5.557 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 355 of 531 SUCCESS (0 secs 
/ 5.56 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 356 of 531 SUCCESS (0 secs 
/ 5.564 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 357 of 531 SUCCESS (0 secs 
/ 5.571 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 358 of 531 SUCCESS (0 secs 
/ 5.574 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 359 of 531 SUCCESS (0 secs 
/ 5.577 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 360 of 531 SUCCESS (0 secs 
/ 5.579 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 361 of 531 SUCCESS (0 secs 
/ 5.584 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 362 of 531 SUCCESS (0 secs 
/ 5.587 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 363 of 531 SUCCESS (0 secs 
/ 5.591 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 364 of 531 SUCCESS (0 secs 
/ 5.599 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 365 of 531 SUCCESS (0 secs 
/ 5.602 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 366 of 531 SUCCESS (0 secs 
/ 5.605 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 367 of 531 SUCCESS (0 secs 
/ 5.608 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 368 of 531 SUCCESS (0 secs 
/ 5.611 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 369 of 531 SUCCESS (0 secs 
/ 5.615 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 370 of 531 SUCCESS (0 secs 
/ 5.619 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 371 of 531 SUCCESS (0 secs 
/ 5.625 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 372 of 531 SUCCESS (0 secs 
/ 5.628 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 373 of 531 SUCCESS (0 secs 
/ 5.632 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 374 of 531 SUCCESS (0 secs 
/ 5.635 secs)
HeadlessChrome 0.0.0

Build failed in Jenkins: pgadmin4-master-python26 #736

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Using the 'webcabin-docker' from new repository, which contains 
fixed

[Ashesh Vashi] Change the order of the shims in the shims file.

[Ashesh Vashi] Using the latest version (v2.3.0) of jquery.event.drag to fix the

--
[...truncated 707.23 KB...]
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 327 of 531 SUCCESS (0 secs 
/ 5.39 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 328 of 531 SUCCESS (0 secs 
/ 5.393 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 329 of 531 SUCCESS (0 secs 
/ 5.397 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 330 of 531 SUCCESS (0 secs 
/ 5.4 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 331 of 531 SUCCESS (0 secs 
/ 5.403 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 332 of 531 SUCCESS (0 secs 
/ 5.406 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 333 of 531 SUCCESS (0 secs 
/ 5.41 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 334 of 531 SUCCESS (0 secs 
/ 5.415 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 335 of 531 SUCCESS (0 secs 
/ 5.42 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 336 of 531 SUCCESS (0 secs 
/ 5.423 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 337 of 531 SUCCESS (0 secs 
/ 5.426 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 338 of 531 SUCCESS (0 secs 
/ 5.43 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 339 of 531 SUCCESS (0 secs 
/ 5.433 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 340 of 531 SUCCESS (0 secs 
/ 5.436 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 341 of 531 SUCCESS (0 secs 
/ 5.44 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 342 of 531 SUCCESS (0 secs 
/ 5.443 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 343 of 531 SUCCESS (0 secs 
/ 5.447 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 344 of 531 SUCCESS (0 secs 
/ 5.453 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 345 of 531 SUCCESS (0 secs 
/ 5.457 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 346 of 531 SUCCESS (0 secs 
/ 5.46 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 347 of 531 SUCCESS (0 secs 
/ 5.464 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 348 of 531 SUCCESS (0 secs 
/ 5.467 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 349 of 531 SUCCESS (0 secs 
/ 5.47 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 350 of 531 SUCCESS (0 secs 
/ 5.473 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 351 of 531 SUCCESS (0 secs 
/ 5.479 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 352 of 531 SUCCESS (0 secs 
/ 5.485 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 353 of 531 SUCCESS (0 secs 
/ 5.488 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 354 of 531 SUCCESS (0 secs 
/ 5.492 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 355 of 531 SUCCESS (0 secs 
/ 5.502 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 356 of 531 SUCCESS (0 secs 
/ 5.507 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 357 of 531 SUCCESS (0 secs 
/ 5.513 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 358 of 531 SUCCESS (0 secs 
/ 5.516 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 359 of 531 SUCCESS (0 secs 
/ 5.519 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 360 of 531 SUCCESS (0 secs 
/ 5.522 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 361 of 531 SUCCESS (0 secs 
/ 5.525 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 362 of 531 SUCCESS (0 secs 
/ 5.529 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 363 of 531 SUCCESS (0 secs 
/ 5.533 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 364 of 531 SUCCESS (0 secs 
/ 5.539 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 365 of 531 SUCCESS (0 secs 
/ 5.543 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 366 of 531 SUCCESS (0 secs 
/ 5.546 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 367 of 531 SUCCESS (0 secs 
/ 5.549 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 368 of 531 SUCCESS (0 secs 
/ 5.551 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 369 of 531 SUCCESS (0 secs 
/ 5.553 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 370 of 531 SUCCESS (0 secs 
/ 5.557 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 371 of 531 SUCCESS (0 secs 
/ 5.562 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 372 of 531 SUCCESS (0 secs 
/ 5.565 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 373 of 531 SUCCESS (0 secs 
/ 5.568 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 374 of 531 SUCCESS (0 secs 
/ 5.573 secs)
HeadlessChrome 0.0.0 (Linu

Build failed in Jenkins: pgadmin4-master-python36 #599

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Change the order of the shims in the shims file.

[Ashesh Vashi] Using the latest version (v2.3.0) of jquery.event.drag to fix the

--
[...truncated 703.40 KB...]
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 327 of 531 SUCCESS (0 secs 
/ 5.347 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 328 of 531 SUCCESS (0 secs 
/ 5.35 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 329 of 531 SUCCESS (0 secs 
/ 5.353 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 330 of 531 SUCCESS (0 secs 
/ 5.356 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 331 of 531 SUCCESS (0 secs 
/ 5.359 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 332 of 531 SUCCESS (0 secs 
/ 5.363 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 333 of 531 SUCCESS (0 secs 
/ 5.366 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 334 of 531 SUCCESS (0 secs 
/ 5.37 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 335 of 531 SUCCESS (0 secs 
/ 5.376 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 336 of 531 SUCCESS (0 secs 
/ 5.38 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 337 of 531 SUCCESS (0 secs 
/ 5.383 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 338 of 531 SUCCESS (0 secs 
/ 5.386 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 339 of 531 SUCCESS (0 secs 
/ 5.389 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 340 of 531 SUCCESS (0 secs 
/ 5.392 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 341 of 531 SUCCESS (0 secs 
/ 5.396 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 342 of 531 SUCCESS (0 secs 
/ 5.399 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 343 of 531 SUCCESS (0 secs 
/ 5.403 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 344 of 531 SUCCESS (0 secs 
/ 5.409 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 345 of 531 SUCCESS (0 secs 
/ 5.413 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 346 of 531 SUCCESS (0 secs 
/ 5.416 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 347 of 531 SUCCESS (0 secs 
/ 5.419 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 348 of 531 SUCCESS (0 secs 
/ 5.422 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 349 of 531 SUCCESS (0 secs 
/ 5.425 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 350 of 531 SUCCESS (0 secs 
/ 5.429 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 351 of 531 SUCCESS (0 secs 
/ 5.433 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 352 of 531 SUCCESS (0 secs 
/ 5.439 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 353 of 531 SUCCESS (0 secs 
/ 5.442 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 354 of 531 SUCCESS (0 secs 
/ 5.445 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 355 of 531 SUCCESS (0 secs 
/ 5.448 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 356 of 531 SUCCESS (0 secs 
/ 5.452 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 357 of 531 SUCCESS (0 secs 
/ 5.46 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 358 of 531 SUCCESS (0 secs 
/ 5.469 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 359 of 531 SUCCESS (0 secs 
/ 5.472 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 360 of 531 SUCCESS (0 secs 
/ 5.476 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 361 of 531 SUCCESS (0 secs 
/ 5.48 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 362 of 531 SUCCESS (0 secs 
/ 5.483 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 363 of 531 SUCCESS (0 secs 
/ 5.487 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 364 of 531 SUCCESS (0 secs 
/ 5.492 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 365 of 531 SUCCESS (0 secs 
/ 5.494 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 366 of 531 SUCCESS (0 secs 
/ 5.497 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 367 of 531 SUCCESS (0 secs 
/ 5.5 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 368 of 531 SUCCESS (0 secs 
/ 5.503 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 369 of 531 SUCCESS (0 secs 
/ 5.506 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 370 of 531 SUCCESS (0 secs 
/ 5.51 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 371 of 531 SUCCESS (0 secs 
/ 5.516 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 372 of 531 SUCCESS (0 secs 
/ 5.521 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 373 of 531 SUCCESS (0 secs 
/ 5.525 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 374 of 531 SUCCESS (0 secs 
/ 5.529 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 375 of 531 SUCCESS (0 secs 
/ 5.532 secs)
HeadlessChrome 0.

Build failed in Jenkins: pgadmin4-master-python33 #606

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Using the latest version (v2.3.0) of jquery.event.drag to fix the

--
[...truncated 703.76 KB...]
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 327 of 531 SUCCESS (0 secs 
/ 5.405 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 328 of 531 SUCCESS (0 secs 
/ 5.408 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 329 of 531 SUCCESS (0 secs 
/ 5.411 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 330 of 531 SUCCESS (0 secs 
/ 5.414 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 331 of 531 SUCCESS (0 secs 
/ 5.417 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 332 of 531 SUCCESS (0 secs 
/ 5.42 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 333 of 531 SUCCESS (0 secs 
/ 5.423 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 334 of 531 SUCCESS (0 secs 
/ 5.427 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 335 of 531 SUCCESS (0 secs 
/ 5.433 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 336 of 531 SUCCESS (0 secs 
/ 5.436 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 337 of 531 SUCCESS (0 secs 
/ 5.44 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 338 of 531 SUCCESS (0 secs 
/ 5.443 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 339 of 531 SUCCESS (0 secs 
/ 5.447 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 340 of 531 SUCCESS (0 secs 
/ 5.45 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 341 of 531 SUCCESS (0 secs 
/ 5.453 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 342 of 531 SUCCESS (0 secs 
/ 5.456 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 343 of 531 SUCCESS (0 secs 
/ 5.46 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 344 of 531 SUCCESS (0 secs 
/ 5.466 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 345 of 531 SUCCESS (0 secs 
/ 5.47 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 346 of 531 SUCCESS (0 secs 
/ 5.473 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 347 of 531 SUCCESS (0 secs 
/ 5.476 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 348 of 531 SUCCESS (0 secs 
/ 5.479 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 349 of 531 SUCCESS (0 secs 
/ 5.482 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 350 of 531 SUCCESS (0 secs 
/ 5.485 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 351 of 531 SUCCESS (0 secs 
/ 5.49 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 352 of 531 SUCCESS (0 secs 
/ 5.496 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 353 of 531 SUCCESS (0 secs 
/ 5.499 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 354 of 531 SUCCESS (0 secs 
/ 5.501 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 355 of 531 SUCCESS (0 secs 
/ 5.505 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 356 of 531 SUCCESS (0 secs 
/ 5.509 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 357 of 531 SUCCESS (0 secs 
/ 5.515 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 358 of 531 SUCCESS (0 secs 
/ 5.519 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 359 of 531 SUCCESS (0 secs 
/ 5.522 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 360 of 531 SUCCESS (0 secs 
/ 5.525 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 361 of 531 SUCCESS (0 secs 
/ 5.528 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 362 of 531 SUCCESS (0 secs 
/ 5.531 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 363 of 531 SUCCESS (0 secs 
/ 5.537 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 364 of 531 SUCCESS (0 secs 
/ 5.543 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 365 of 531 SUCCESS (0 secs 
/ 5.546 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 366 of 531 SUCCESS (0 secs 
/ 5.551 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 367 of 531 SUCCESS (0 secs 
/ 5.553 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 368 of 531 SUCCESS (0 secs 
/ 5.556 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 369 of 531 SUCCESS (0 secs 
/ 5.558 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 370 of 531 SUCCESS (0 secs 
/ 5.562 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 371 of 531 SUCCESS (0 secs 
/ 5.57 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 372 of 531 SUCCESS (0 secs 
/ 5.573 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 373 of 531 SUCCESS (0 secs 
/ 5.576 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 374 of 531 SUCCESS (0 secs 
/ 5.579 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 375 of 531 SUCCESS (0 secs 
/ 5.604 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 376 of 531 SUCCESS (0 secs 
/ 5.611

Build failed in Jenkins: pgadmin4-master-python34 #593

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Using the latest version (v2.3.0) of jquery.event.drag to fix the

--
[...truncated 703.41 KB...]
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 327 of 531 SUCCESS (0 secs 
/ 5.373 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 328 of 531 SUCCESS (0 secs 
/ 5.377 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 329 of 531 SUCCESS (0 secs 
/ 5.38 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 330 of 531 SUCCESS (0 secs 
/ 5.382 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 331 of 531 SUCCESS (0 secs 
/ 5.384 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 332 of 531 SUCCESS (0 secs 
/ 5.387 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 333 of 531 SUCCESS (0 secs 
/ 5.391 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 334 of 531 SUCCESS (0 secs 
/ 5.395 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 335 of 531 SUCCESS (0 secs 
/ 5.4 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 336 of 531 SUCCESS (0 secs 
/ 5.404 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 337 of 531 SUCCESS (0 secs 
/ 5.407 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 338 of 531 SUCCESS (0 secs 
/ 5.41 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 339 of 531 SUCCESS (0 secs 
/ 5.413 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 340 of 531 SUCCESS (0 secs 
/ 5.416 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 341 of 531 SUCCESS (0 secs 
/ 5.42 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 342 of 531 SUCCESS (0 secs 
/ 5.422 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 343 of 531 SUCCESS (0 secs 
/ 5.425 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 344 of 531 SUCCESS (0 secs 
/ 5.43 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 345 of 531 SUCCESS (0 secs 
/ 5.434 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 346 of 531 SUCCESS (0 secs 
/ 5.437 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 347 of 531 SUCCESS (0 secs 
/ 5.44 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 348 of 531 SUCCESS (0 secs 
/ 5.443 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 349 of 531 SUCCESS (0 secs 
/ 5.446 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 350 of 531 SUCCESS (0 secs 
/ 5.452 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 351 of 531 SUCCESS (0 secs 
/ 5.456 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 352 of 531 SUCCESS (0 secs 
/ 5.462 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 353 of 531 SUCCESS (0 secs 
/ 5.466 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 354 of 531 SUCCESS (0 secs 
/ 5.475 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 355 of 531 SUCCESS (0 secs 
/ 5.479 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 356 of 531 SUCCESS (0 secs 
/ 5.484 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 357 of 531 SUCCESS (0 secs 
/ 5.49 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 358 of 531 SUCCESS (0 secs 
/ 5.493 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 359 of 531 SUCCESS (0 secs 
/ 5.496 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 360 of 531 SUCCESS (0 secs 
/ 5.5 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 361 of 531 SUCCESS (0 secs 
/ 5.503 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 362 of 531 SUCCESS (0 secs 
/ 5.507 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 363 of 531 SUCCESS (0 secs 
/ 5.511 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 364 of 531 SUCCESS (0 secs 
/ 5.518 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 365 of 531 SUCCESS (0 secs 
/ 5.52 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 366 of 531 SUCCESS (0 secs 
/ 5.522 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 367 of 531 SUCCESS (0 secs 
/ 5.524 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 368 of 531 SUCCESS (0 secs 
/ 5.528 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 369 of 531 SUCCESS (0 secs 
/ 5.531 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 370 of 531 SUCCESS (0 secs 
/ 5.535 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 371 of 531 SUCCESS (0 secs 
/ 5.541 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 372 of 531 SUCCESS (0 secs 
/ 5.545 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 373 of 531 SUCCESS (0 secs 
/ 5.548 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 374 of 531 SUCCESS (0 secs 
/ 5.551 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 375 of 531 SUCCESS (0 secs 
/ 5.555 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 376 of 531 SUCCESS (0 secs 
/ 5.558 secs

Build failed in Jenkins: pgadmin4-master-python27 #605

2018-05-10 Thread pgAdmin 4 Jenkins 
See 


Changes:

[Ashesh Vashi] Using the latest version (v2.3.0) of jquery.event.drag to fix the

--
[...truncated 705.69 KB...]
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 327 of 531 SUCCESS (0 secs 
/ 5.352 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 328 of 531 SUCCESS (0 secs 
/ 5.355 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 329 of 531 SUCCESS (0 secs 
/ 5.358 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 330 of 531 SUCCESS (0 secs 
/ 5.361 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 331 of 531 SUCCESS (0 secs 
/ 5.364 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 332 of 531 SUCCESS (0 secs 
/ 5.369 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 333 of 531 SUCCESS (0 secs 
/ 5.372 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 334 of 531 SUCCESS (0 secs 
/ 5.376 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 335 of 531 SUCCESS (0 secs 
/ 5.382 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 336 of 531 SUCCESS (0 secs 
/ 5.386 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 337 of 531 SUCCESS (0 secs 
/ 5.388 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 338 of 531 SUCCESS (0 secs 
/ 5.391 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 339 of 531 SUCCESS (0 secs 
/ 5.394 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 340 of 531 SUCCESS (0 secs 
/ 5.397 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 341 of 531 SUCCESS (0 secs 
/ 5.401 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 342 of 531 SUCCESS (0 secs 
/ 5.404 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 343 of 531 SUCCESS (0 secs 
/ 5.408 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 344 of 531 SUCCESS (0 secs 
/ 5.415 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 345 of 531 SUCCESS (0 secs 
/ 5.417 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 346 of 531 SUCCESS (0 secs 
/ 5.419 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 347 of 531 SUCCESS (0 secs 
/ 5.422 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 348 of 531 SUCCESS (0 secs 
/ 5.425 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 349 of 531 SUCCESS (0 secs 
/ 5.429 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 350 of 531 SUCCESS (0 secs 
/ 5.433 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 351 of 531 SUCCESS (0 secs 
/ 5.437 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 352 of 531 SUCCESS (0 secs 
/ 5.443 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 353 of 531 SUCCESS (0 secs 
/ 5.446 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 354 of 531 SUCCESS (0 secs 
/ 5.449 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 355 of 531 SUCCESS (0 secs 
/ 5.452 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 356 of 531 SUCCESS (0 secs 
/ 5.456 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 357 of 531 SUCCESS (0 secs 
/ 5.463 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 358 of 531 SUCCESS (0 secs 
/ 5.466 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 359 of 531 SUCCESS (0 secs 
/ 5.469 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 360 of 531 SUCCESS (0 secs 
/ 5.472 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 361 of 531 SUCCESS (0 secs 
/ 5.478 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 362 of 531 SUCCESS (0 secs 
/ 5.483 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 363 of 531 SUCCESS (0 secs 
/ 5.487 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 364 of 531 SUCCESS (0 secs 
/ 5.493 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 365 of 531 SUCCESS (0 secs 
/ 5.496 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 366 of 531 SUCCESS (0 secs 
/ 5.5 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 367 of 531 SUCCESS (0 secs 
/ 5.503 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 368 of 531 SUCCESS (0 secs 
/ 5.506 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 369 of 531 SUCCESS (0 secs 
/ 5.511 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 370 of 531 SUCCESS (0 secs 
/ 5.515 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 371 of 531 SUCCESS (0 secs 
/ 5.521 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 372 of 531 SUCCESS (0 secs 
/ 5.525 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 373 of 531 SUCCESS (0 secs 
/ 5.535 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 374 of 531 SUCCESS (0 secs 
/ 5.537 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 375 of 531 SUCCESS (0 secs 
/ 5.541 secs)
HeadlessChrome 0.0.0 (Linux 0.0.0): Executed 376 of 531 SUCCESS (0 secs 
/ 5

pgAdmin 4 commit: Revert back to jquery version 1.12.4 until we fix the

2018-05-10 Thread Ashesh Vashi 
Revert back to jquery version 1.12.4 until we fix the jasmine testsuite, which 
is failing with jQuery (v3.0+)

Branch
--
master

Details
---
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=ccdc1a6c74629d45ed634d6640f54ff55dff2fcd

Modified Files
--
web/package.json |  2 +-
web/yarn.lock| 14 +-
2 files changed, 10 insertions(+), 6 deletions(-)

pgAdmin 4 commit: Using the latest version (v2.3.0) of jquery.event.dro

2018-05-10 Thread Ashesh Vashi 
Using the latest version (v2.3.0) of jquery.event.drop.

Branch
--
master

Details
---
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=e17b62c055a6ee6f3ff50720dda7fc7e155d3214
Author: Murtuza Zabuawala 

Modified Files
--
web/webpack.shim.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Jenkins build is back to normal : pgadmin4-master-python26 #737

2018-05-10 Thread pgAdmin 4 Jenkins 
See

Jenkins build is back to normal : pgadmin4-master-python34 #594

2018-05-10 Thread pgAdmin 4 Jenkins 
See

Jenkins build is back to normal : pgadmin4-master-python36 #600

2018-05-10 Thread pgAdmin 4 Jenkins 
See

Re: [pgAdmin4][Patch] Feature #3270 Add support for running regression tests against Firefox

2018-05-10 Thread Dave Page 
Hi

On Wed, May 9, 2018 at 2:55 PM, Akshay Joshi 
wrote:

> Hi
>
> On Wed, May 9, 2018 at 6:19 PM, Dave Page  wrote:
>
>> Hi
>>
>> On Wed, May 9, 2018 at 8:10 AM, Akshay Joshi <
>> akshay.jo...@enterprisedb.com> wrote:
>>
>>> Thanks Anthony for fixing those two test cases. I have verified it and
>>> patch looks good to me.
>>> Attached is the modified patch where I have remove "import time" which
>>> is not required and update the retry message from 10 to 60.
>>>
>>> To be honest I have seen some intermittent "Timeout" issues on *Chrome*
>>> and *FireFox *and those issues are not consistent for any particular
>>> test case.
>>>
>>> @Hackers, Please review it and if it looks good then commit it.
>>>
>>
>> I seem to be getting the following failures consistently (screenshots
>> attached):
>>
>> ==
>> ERROR: runTest (pgadmin.feature_tests.pg_data
>> type_validation_test.PGDataypeFeatureTest)
>> Test checks for PG data-types output
>> --
>> Traceback (most recent call last):
>>   File 
>> "/Users/dpage/git/pgadmin4/web/pgadmin/feature_tests/pg_datatype_validation_test.py",
>> line 135, in runTest
>> self._check_datatype()
>>   File 
>> "/Users/dpage/git/pgadmin4/web/pgadmin/feature_tests/pg_datatype_validation_test.py",
>> line 169, in _check_datatype
>> "contains(.,'{}')]".format(batch['datatype'][0])
>>   File "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/site-packa
>> ges/selenium/webdriver/support/wait.py", line 80, in until
>> raise TimeoutException(message, screen, stacktrace)
>> TimeoutException: Message:
>>
>
> This is the intermittent issue I was highlighted in my previous
> email.
>

Right - except I'm getting it consistently, on every run I've done.


>
>>
>> ==
>> FAIL: runTest (pgadmin.feature_tests.xss_che
>> cks_file_manager_test.CheckFileManagerFeatureTest)
>> Tests to check if File manager is vulnerable to XSS
>> --
>> Traceback (most recent call last):
>>   File 
>> "/Users/dpage/git/pgadmin4/web/pgadmin/feature_tests/xss_checks_file_manager_test.py",
>> line 60, in runTest
>> self._open_file_manager_and_check_xss_file()
>>   File 
>> "/Users/dpage/git/pgadmin4/web/pgadmin/feature_tests/xss_checks_file_manager_test.py",
>> line 110, in _open_file_manager_and_check_xss_file
>> 'File manager'
>>   File 
>> "/Users/dpage/git/pgadmin4/web/pgadmin/feature_tests/xss_checks_file_manager_test.py",
>> line 117, in _check_escaped_characters
>> ) != -1, "{0} might be vulnerable to XSS ".format(source)
>> AssertionError: File manager might be vulnerable to XSS
>>
>
> I have removed Anthony's patch and added time.sleep(0.05) before and
> after reading the content from the file.
>

That part works now; however, Anthony's method is the more correct way to
handle this. Is the issue with his patch that waiting for the element to
load isn't enough, and we have to wait for it to load *and* for something
else to become active or dynamically load? In other words, are we waiting
for the right thing?


>
>> --
>> Ran 11 tests in 475.292s
>>
>> FAILED (failures=1, errors=1)
>>
>> ==
>> Test Result Summary
>> ==
>>
>> Regression - PG 9.4:
>>
>> 9 tests passed
>> 2 tests failed:
>> CheckFileManagerFeatureTest (Tests to check if File manager is vulnerable
>> to XSS)
>> PGDataypeFeatureTest (Test checks for PG data-types output)
>> 0 tests skipped
>>
>> ==
>>
>> Please check output in file: /Users/dpage/git/pgadmin4/web/
>> regression/regression.log
>>
>> make: *** [check-feature] Error 1
>>
>>
>
>Attached is the modified patch with all test cases passed on my
> machine. I have tried couple of times (refer the attached screenshot).
>
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>
>
>
> --
> *Akshay Joshi*
>
> *Sr. Software Architect *
>
>
>
> *Phone: +91 20-3058-9517Mobile: +91 976-788-8246*
>



-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Jenkins build is back to normal : pgadmin4-master-python33 #607

2018-05-10 Thread pgAdmin 4 Jenkins 
See

Jenkins build is back to normal : pgadmin4-master-python35 #603

2018-05-10 Thread pgAdmin 4 Jenkins 
See

Jenkins build is back to normal : pgadmin4-master-python27 #606

2018-05-10 Thread pgAdmin 4 Jenkins 
See

GSoC Introduction - Implement geospatial data viewer in pgAdmin4 for PostGIS

2018-05-10 Thread Xuri Gong 
Hi everyone,

My name is Xuri Gong from PostGIS community. I am selected for Google
Summer of Code(GSoC)  2018 and will be working on implementing geospatial
data viewer in pgAdmin4 for PostGIS.

I find the related feature "Support map view for PostGIS query result sets"
in this link:
https://redmine.postgresql.org/issues/1407

It was added about 2 years ago with a short description. Now I am writing
the software design documents and it will be really helpful if you could
give me any suggestions. Below is the link of my proposal:
https://docs.google.com/document/d/1MH54gIlQpbx56uVx5e_
QNP4MWp9NoFdsCcWUFRGBESo/edit?usp=sharing

Here is my project's wiki page:
https://trac.osgeo.org/postgis/wiki/GeospatialDataViewerInPgAdmin4ForPostGIS

Here is my public repository:
https://github.com/Gooong/pgadmin4

Regards,
Xuri Gong

[pgAdmin4][Patch]: RM #3277 Runtime startup error handling is broken on Windows.

2018-05-10 Thread Akshay Joshi 
Hi Hackers,

Please find the attached patch to fix RM #3277 Runtime startup error
handling is broken on Windows.

This issue is regression of RM #3177 "Sporadically crashes on Windows when
exit". Where below code of pgAdmin4.cpp creates the problem:
*QObject::connect(server, SIGNAL(finished()), server, SLOT(deleteLater()));*

In case when PythonPath is not provided then application server not started
and server thread finished there execution, due to the above line of code
*Destructor* of Server class has been called and we are accessing the
function *server->getError().length() *at line no 251 of pgAdmin4.cpp,
which cause the application crash.

I have removed that line and tested RM #3177 and RM# 3277, both are working
fine.

Please review and test it.

-- 
*Akshay Joshi*

*Sr. Software Architect *



*Phone: +91 20-3058-9517Mobile: +91 976-788-8246*


RM_3277.patch
Description: Binary data

Re: [pgAdmin4][Patch]: RM #3277 Runtime startup error handling is broken on Windows.

2018-05-10 Thread Dave Page 
Hi

On Thu, May 10, 2018 at 2:00 PM, Akshay Joshi  wrote:

> Hi Hackers,
>
> Please find the attached patch to fix RM #3277 Runtime startup error
> handling is broken on Windows.
>
> This issue is regression of RM #3177 "Sporadically crashes on Windows when
> exit". Where below code of pgAdmin4.cpp creates the problem:
> *QObject::connect(server, SIGNAL(finished()), server,
> SLOT(deleteLater()));*
>
> In case when PythonPath is not provided then application server not
> started and server thread finished there execution, due to the above line
> of code *Destructor* of Server class has been called and we are accessing
> the function *server->getError().length() *at line no 251 of pgAdmin4.cpp,
> which cause the application crash.
>
> I have removed that line and tested RM #3177 and RM# 3277, both are
> working fine.
>
> Please review and test it.
>

So my first test was compiled against Python 3, but my config was still
pointing at a Python 2 venv. I got the error below in the console of
QtCreator.

Also, wouldn't it make more sense to move the connect that you removed so
it only happens once the server is up and running? That way we will still
ensure it gets properly deleted when appropriate, but not prematurely if an
error occurs during startup.

 Starting /Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_
10_1_clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4...
Python path:  "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/site-
packages:/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7"
Python Home:  ""
Fatal Python error: Py_Initialize: unable to load the file system codec
  File "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/encodings/__init__.py",
line 123
raise CodecRegistryError,\
^
SyntaxError: invalid syntax

Current thread 0x7fffcbb433c0 (most recent call first):
The program has unexpectedly finished.
/Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_
10_1_clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4 crashed.

Starting /Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_
10_1_clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4...
Python path:  "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/site-
packages:/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7"
Python Home:  ""
Fatal Python error: Py_Initialize: unable to load the file system codec
  File "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/encodings/__init__.py",
line 123
raise CodecRegistryError,\
^
SyntaxError: invalid syntax

Current thread 0x7fffcbb433c0 (most recent call first):
The program has unexpectedly finished.
/Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_
10_1_clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4 crashed.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: [pgAdmin4][Patch]: RM #3277 Runtime startup error handling is broken on Windows.

2018-05-10 Thread Akshay Joshi 
Hi

On Thu, May 10, 2018 at 7:38 PM, Dave Page  wrote:

> Hi
>
> On Thu, May 10, 2018 at 2:00 PM, Akshay Joshi <
> akshay.jo...@enterprisedb.com> wrote:
>
>> Hi Hackers,
>>
>> Please find the attached patch to fix RM #3277 Runtime startup error
>> handling is broken on Windows.
>>
>> This issue is regression of RM #3177 "Sporadically crashes on Windows
>> when exit". Where below code of pgAdmin4.cpp creates the problem:
>> *QObject::connect(server, SIGNAL(finished()), server,
>> SLOT(deleteLater()));*
>>
>> In case when PythonPath is not provided then application server not
>> started and server thread finished there execution, due to the above line
>> of code *Destructor* of Server class has been called and we are
>> accessing the function *server->getError().length() *at line no 251 of
>> pgAdmin4.cpp, which cause the application crash.
>>
>> I have removed that line and tested RM #3177 and RM# 3277, both are
>> working fine.
>>
>> Please review and test it.
>>
>
> So my first test was compiled against Python 3, but my config was still
> pointing at a Python 2 venv. I got the error below in the console of
> QtCreator.
>
> Also, wouldn't it make more sense to move the connect that you removed so
> it only happens once the server is up and running? That way we will still
> ensure it gets properly deleted when appropriate, but not prematurely if an
> error occurs during startup.
>

   Agreed, I have move that call to other place when server is up and
running. Attached is the modified patch.

>
>  Starting /Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_10_1_
> clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4...
> Python path:  "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/site-packa
> ges:/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7"
> Python Home:  ""
> Fatal Python error: Py_Initialize: unable to load the file system codec
>   File 
> "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/encodings/__init__.py",
> line 123
> raise CodecRegistryError,\
> ^
> SyntaxError: invalid syntax
>
> Current thread 0x7fffcbb433c0 (most recent call first):
> The program has unexpectedly finished.
> /Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_10_1_
> clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4 crashed.
>
> Starting /Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_10_1_
> clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4...
> Python path:  "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/site-packa
> ges:/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7"
> Python Home:  ""
> Fatal Python error: Py_Initialize: unable to load the file system codec
>   File 
> "/Users/dpage/.virtualenvs/pgadmin4/lib/python2.7/encodings/__init__.py",
> line 123
> raise CodecRegistryError,\
> ^
> SyntaxError: invalid syntax
>
> Current thread 0x7fffcbb433c0 (most recent call first):
> The program has unexpectedly finished.
> /Users/dpage/git/pgadmin4/build-pgAdmin4-Desktop_Qt_5_10_1_
> clang_64bit-Debug/pgAdmin4.app/Contents/MacOS/pgAdmin4 crashed.
>

Yes, it is reproducible. I have tried putting try catch around "
*Py_Initialize*", but no success.


>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>



-- 
*Akshay Joshi*

*Sr. Software Architect *



*Phone: +91 20-3058-9517Mobile: +91 976-788-8246*


RM_3277_v2.patch
Description: Binary data

Re: JS Test error on Windows

2018-05-10 Thread Aditya Toshniwal 
Hi Dave/Hackers,

PFA fix for the problem. The RegEx for webpack test is not working on
windows because the path separator is different for Windows( \ ) and Unix(
/ ). And so, the imports loader is not executing for slickgrid.
Patch tested on Win 10, Win 7, Ubuntu, Cent OS and works fine.

Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"

On Fri, Apr 27, 2018 at 5:34 PM, Dave Page  wrote:

>
>
> On Fri, Apr 27, 2018 at 10:49 AM, Murtuza Zabuawala  enterprisedb.com> wrote:
>
>> Not sure if that's the case but possibly security mechanism on Win2016
>> somehow interfering with Headless chrome execution.
>>
>
> Maybe - I cannot find anything obvious through Google though. I have
> already disabled the firewall entirely.
>
>
>>
>>
>> On Fri, Apr 27, 2018 at 2:44 PM, Dave Page  wrote:
>>
>>> Anyone? Khushboo, Murtuza; any ideas?
>>>
>>> On Wed, Apr 25, 2018 at 4:45 PM, Dave Page  wrote:
>>>
 Hi

 Setting up an new build system running Windows 2016 and I'm hitting an
 error with the JS tests as below. I have Yarn 1.6.0, Node 8.11.1 and get
 the following error running yarn run test:karma-once. The linter and
 bundler work fine, FWIW, and I see the same error running either manually
 or through Jenkins. jquery.event.drag 2.2 and 2.3.0 are in the slickgrid
 lib directory. Chrome is 66.0.3359.117.

 Does anyone have any idea what's going on?

 webpack: Compiled successfully.
 HeadlessChrome 0.0.0 (Windows 10 0.0.0) ERROR
   {
 "message": "Uncaught Error: SlickGrid requires jquery.event.drag
 module to be loaded\nat regression/javascript/selectio
 n/column_selector_spec.js:13842:3\n\nError: SlickGrid requires
 jquery.event.drag module to be loaded\nat Object.
 (regression/javascript/selection/column_selector_spec.js:13842:9)\n
 at Object.5 (regression/javascript/selecti
 on/column_selector_spec.js:17810:30)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at Object.904 (regression/javascript/selecti
 on/column_selector_spec.js:18335:1)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at regression/javascript/selection/column_selector_spec.js:63:18\n
 at regression/javascript/selection/column_selector_spec.js:66:10",
 "str": "Uncaught Error: SlickGrid requires jquery.event.drag module
 to be loaded\nat regression/javascript/selectio
 n/column_selector_spec.js:13842:3\n\nError: SlickGrid requires
 jquery.event.drag module to be loaded\nat Object.
 (regression/javascript/selection/column_selector_spec.js:13842:9)\n
 at Object.5 (regression/javascript/selecti
 on/column_selector_spec.js:17810:30)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at Object.904 (regression/javascript/selecti
 on/column_selector_spec.js:18335:1)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at regression/javascript/selection/column_selector_spec.js:63:18\n
 at regression/javascript/selection/column_selector_spec.js:66:10"
   }

 HeadlessChrome 0.0.0 (Windows 10 0.0.0) ERROR
   {
 "message": "Uncaught Error: SlickGrid requires jquery.event.drag
 module to be loaded\nat regression/javascript/selectio
 n/column_selector_spec.js:13842:3\n\nError: SlickGrid requires
 jquery.event.drag module to be loaded\nat Object.
 (regression/javascript/selection/column_selector_spec.js:13842:9)\n
 at Object.5 (regression/javascript/selecti
 on/column_selector_spec.js:17810:30)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at Object.904 (regression/javascript/selecti
 on/column_selector_spec.js:18335:1)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at regression/javascript/selection/column_selector_spec.js:63:18\n
 at regression/javascript/selection/column_selector_spec.js:66:10",
 "str": "Uncaught Error: SlickGrid requires jquery.event.drag module
 to be loaded\nat regression/javascript/selectio
 n/column_selector_spec.js:13842:3\n\nError: SlickGrid requires
 jquery.event.drag module to be loaded\nat Object.
 (regression/javascript/selection/column_selector_spec.js:13842:9)\n
 at Object.5 (regression/javascript/selecti
 on/column_selector_spec.js:17810:30)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at Object.904 (regression/javascript/selecti
 on/column_selector_spec.js:18335:1)\nat __webpack_require__
 (regression/javascript/selection/column_selector_spec.js:20:30)\n
 at regression/javascript/selection/column_selector_spec.js:6

Re: [pgadmin4][patch] Initial patch to decouple from ACI Tree

2018-05-10 Thread Ashesh Vashi 
On Thu, May 10, 2018 at 8:08 PM, Anthony Emengo  wrote:

> 1. In TreeNode, we're keepging the reference of DOMElement, do we really
>> need it?
>
> As of right now, our Tree abstraction acts as an adapter to the aciTree
> library. The aciTree library needs the domElement for most of its functions
> (setInode, unload, etc). Thus this is the easiest way to introduce our
> abstraction and keep the functionality as before - at least until we decide
> that whether we want to switch out the library or not.
>
I understand that. But - I've not seen any reference of domElement the code
yet, hence - pointed that out.

> 2. Are you expecting the tree class to be a singleton class
>
> Since this tree is referenced throughout the codebase, considering it to
> be a singleton seems like the most appropriate pattern for this usecase. It
> is very much the same way how we create a single instance of the aciTree
> library and use that throughout the codebase. Moreover, it opens up
> opportunities to improve performance, for example caching lockups of nodes.
> I’m not a fan of singletons myself, but I feel like we’re simply keeping
> the architecture the same in the instance.
>
Yeah - I don't see any usage of tree object from anywhere.
And, we're already creating new object in browser.js (and, not utitlizing
that instance anywhere.)

-- Thanks, Ashesh

> ​
>
> Sincerely,
>
> Anthony and Victoria
>